Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated aws_dms_endpoint.engine_name possible values w/ redshift-serverless #33316

Merged

Conversation

mmccarthy404
Copy link

@mmccarthy404 mmccarthy404 commented Sep 5, 2023

AWS DMS currently supports creating endpoint targets for Redshift Serverless w/ the engine name redshift-serverless as seen below:

image

This pull requests enables redshift-serverless as an available option when creating AWS DMS endpoint resources, and the below MvP will successfully deploy an AWS DMS endpoint based on the AWS whitepaper documentation here.

terraform {
  required_providers {
    aws = {
      version = ">= 2.7.0"
      source  = "hashicorp/aws"
    }
  }
}

# Create a new endpoint
resource "aws_dms_endpoint" "test" {
  endpoint_id   = "test-dms-endpoint-tf"
  endpoint_type = "target"
  engine_name   = "redshift-serverless"
  username      = "<USERNAME>"
  password      = "<PASSWORD>"
  port          = 5439
  database_name = "<WORKGROUP ENDPOINT>"
  server_name   = "<WORKGROUP ENDPOINT>"
}

I based this implementation off of the previous one done for Aurora Serverless here: #21174

Because the Aurora Serverless implementation isn't included in the documentation or tests, I left these out to fit the convention, but please let me know if these should be included! 😄

Closes #33075.

@github-actions
Copy link

github-actions bot commented Sep 5, 2023

Community Note

Voting for Prioritization

  • Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions github-actions bot added size/XS Managed by automation to categorize the size of a PR. service/dms Issues and PRs that pertain to the dms service. and removed size/XS Managed by automation to categorize the size of a PR. labels Sep 5, 2023
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 5, 2023
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome @mmccarthy404 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃

@ewbankkit ewbankkit added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. labels Sep 6, 2023
@github-actions github-actions bot added the size/XS Managed by automation to categorize the size of a PR. label Sep 6, 2023
Copy link
Contributor

@ewbankkit ewbankkit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀.

% make testacc TESTARGS='-run=^TestAccDMSEndpoint_basic$$' PKG=dms
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/dms/... -v -count 1 -parallel 20  -run=^TestAccDMSEndpoint_basic$ -timeout 180m
=== RUN   TestAccDMSEndpoint_basic
=== PAUSE TestAccDMSEndpoint_basic
=== CONT  TestAccDMSEndpoint_basic
--- PASS: TestAccDMSEndpoint_basic (91.64s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/dms	97.691s

@ewbankkit
Copy link
Contributor

@mmccarthy404 Thanks for the contribution 🎉 👏.

@ewbankkit ewbankkit merged commit 1dcc5dd into hashicorp:main Sep 6, 2023
31 checks passed
@github-actions github-actions bot added this to the v5.16.0 milestone Sep 6, 2023
@github-actions
Copy link

github-actions bot commented Sep 8, 2023

This functionality has been released in v5.16.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Oct 8, 2023

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/dms Issues and PRs that pertain to the dms service. size/XS Managed by automation to categorize the size of a PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Enhancement]: DMS endpoint redshift-serverless support
2 participants